Dev - #14

Please address the comments from this code review:

## Overall Comments
- The change to read WASM binaries from `deps/` (in `wasmHelper.ts`) means dev runs without `copy-deps.mjs` will fail; consider falling back to `node_modules` when `deps/` is missing so the extension can run directly from the workspace.
- In the new command implementations (`exportJson`, `exportCsv`, `purgeLogs`), `ensureInitialized` is awaited but errors are not surfaced to the user; mirroring the try/catch and `showErrorMessage` behavior used in `openDashboard` would make failures more user-friendly and avoid silent command failures.
- The TreeSitter initialization error message constructed in `parser.ts` is helpful but currently throws the original error after showing a generic message; consider including the original error details in the user-facing message to aid debugging when runtime dependencies are missing or mispackaged.

## Individual Comments

### Comment 1
<location path="src/extension.ts" line_range="228-221" />
<code_context>
+            }
         }),
-        vscode.commands.registerCommand('codepulse.exportJson', () => {
+        vscode.commands.registerCommand('codepulse.exportJson', async () => {
+            await ensureInitialized(context);
             void exportJson();
         }),
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Command handlers using `ensureInitialized` lack error handling, which can surface unhandled rejections to users.

For `codepulse.exportJson`, `codepulse.exportCsv`, and `codepulse.purgeLogs`, `await ensureInitialized(context)` is not wrapped in error handling. If initialization fails (e.g., missing dependencies or DB issues), the command will reject without clear user feedback and may surface opaque errors in the extension host. Please align these handlers with `openDashboard` by using try/catch and `showErrorMessage` to handle initialization failures consistently and avoid unhandled promise rejections.

Suggested implementation:

```typescript
        vscode.commands.registerCommand('codepulse.exportJson', async () => {
            try {
                await ensureInitialized(context);
                void exportJson();
            } catch (err) {
                const msg = err instanceof Error ? err.message : String(err);
                void vscode.window.showErrorMessage(`[CodePulse] Failed to export JSON: ${msg}`);
            }
        }),

```

```typescript
        vscode.commands.registerCommand('codepulse.exportCsv', async () => {
            try {
                await ensureInitialized(context);
                void exportCsv();
            } catch (err) {
                const msg = err instanceof Error ? err.message : String(err);
                void vscode.window.showErrorMessage(`[CodePulse] Failed to export CSV: ${msg}`);
            }
        }),

```

To fully align with the comment, you should also update the `codepulse.purgeLogs` command handler (wherever it is defined in `src/extension.ts`) to follow the same pattern:

- Wrap `await ensureInitialized(context)` and the purge operation in a `try` block.
- On error, compute `msg` using the same `err instanceof Error ? err.message : String(err)` pattern.
- Use `vscode.window.showErrorMessage` with a message like `[CodePulse] Failed to purge logs: ${msg}`.
</issue_to_address>